Documentation
LiveNXResolving Network Route Conflicts Between Docker and LiveNXDownload PDF
Context
Docker was introduced with ClickHouse in LiveNX version 24.2.
After installing LiveNX 24.2, a new interface and route related to Docker appear on the machine because ClickHouse runs in a Docker container.
When you run the ip route command, you might see an entry like this:
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Explanation:
This route is for the Docker network.
Traffic destined for the IP range 172.17.0.0/16 will be handled by the docker0 network interface.
proto kernel means this route was added automatically by the kernel.
scope link means the route is directly connected to the local link.
src 172.17.0.1 specifies the source IP address for this route.
linkdown indicates that the docker0 interface is currently down or inactive.
Summary:
Traffic for the Docker network 172.17.0.0/16 is routed through the docker0 interface, which is currently down.
Ensure that LiveNX devices do not use IP addresses in the 172.17.0.0/16 range to avoid issues. Devices in this range may show as down in LiveNX, and flows may not appear.